-
Notifications
You must be signed in to change notification settings - Fork 600
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add: methology for simulating forking behaviour #1637
Conversation
🔍 Vulnerabilities of
|
digest | sha256:45bb879c069472aecbc4e251d0ddac7b789232b5ecc562b51f3ac5b5bab3b53e |
vulnerabilities | |
platform | linux/amd64 |
size | 154 MB |
packages | 267 |
📦 Base Image greenbone/gvm-libs:unstable
digest | sha256:980524cb59d8cc544bd838a02f8fb47c7bee316f12ed8d56737bb63dce5a122d |
vulnerabilities |
libtasn1-6
|
Affected range | <4.16.0-2+deb11u1 |
Fixed version | 4.16.0-2+deb11u1 |
Description
GNU Libtasn1 before 4.19.0 has an ETYPE_OK off-by-one array size check that affects asn1_encode_simple_der.
openssl 1.1.1n-0+deb11u3
(deb)
pkg:deb/debian/openssl@1.1.1n-0+deb11u3?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | <1.1.1n-0+deb11u5 |
Fixed version | 1.1.1n-0+deb11u5 |
Description
A security vulnerability has been identified in all supported versions of OpenSSL related to the verification of X.509 certificate chains that include policy constraints. Attackers may be able to exploit this vulnerability by creating a malicious certificate chain that triggers exponential use of computational resources, leading to a denial-of-service (DoS) attack on affected systems. Policy processing is disabled by default but can be enabled by passing the
-policy' argument to the command line utilities or by calling the
X509_VERIFY_PARAM_set1_policies()' function.
Affected range | <1.1.1n-0+deb11u4 |
Fixed version | 1.1.1n-0+deb11u4 |
Description
There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
Affected range | <1.1.1n-0+deb11u5 |
Fixed version | 1.1.1n-0+deb11u5 |
Description
Issue summary: Processing some specially crafted ASN.1 object identifiers or data containing them may be very slow. Impact summary: Applications that use OBJ_obj2txt() directly, or use any of the OpenSSL subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS with no message size limit may experience notable to very long delays when processing those messages, which may lead to a Denial of Service. An OBJECT IDENTIFIER is composed of a series of numbers - sub-identifiers - most of which have no size limit. OBJ_obj2txt() may be used to translate an ASN.1 OBJECT IDENTIFIER given in DER encoding form (using the OpenSSL type ASN1_OBJECT) to its canonical numeric text form, which are the sub-identifiers of the OBJECT IDENTIFIER in decimal form, separated by periods. When one of the sub-identifiers in the OBJECT IDENTIFIER is very large (these are sizes that are seen as absurdly large, taking up tens or hundreds of KiBs), the translation to a decimal number in text may take a very long time. The time complexity is O(n^2) with 'n' being the size of the sub-identifiers in bytes (*). With OpenSSL 3.0, support to fetch cryptographic algorithms using names / identifiers in string form was introduced. This includes using OBJECT IDENTIFIERs in canonical numeric text form as identifiers for fetching algorithms. Such OBJECT IDENTIFIERs may be received through the ASN.1 structure AlgorithmIdentifier, which is commonly used in multiple protocols to specify what cryptographic algorithm should be used to sign or verify, encrypt or decrypt, or digest passed data. Applications that call OBJ_obj2txt() directly with untrusted data are affected, with any version of OpenSSL. If the use is for the mere purpose of display, the severity is considered low. In OpenSSL 3.0 and newer, this affects the subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS. It also impacts anything that processes X.509 certificates, including simple things like verifying its signature. The impact on TLS is relatively low, because all versions of OpenSSL have a 100KiB limit on the peer's certificate chain. Additionally, this only impacts clients, or servers that have explicitly enabled client authentication. In OpenSSL 1.1.1 and 1.0.2, this only affects displaying diverse objects, such as X.509 certificates. This is assumed to not happen in such a way that it would cause a Denial of Service, so these versions are considered not affected by this issue in such a way that it would be cause for concern, and the severity is therefore considered low.
Affected range | <1.1.1v-0~deb11u1 |
Fixed version | 1.1.1v-0~deb11u1 |
Description
Issue summary: Checking excessively long DH keys or parameters may be very slow. Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service. The function DH_check() performs various checks on DH parameters. After fixing CVE-2023-3446 it was discovered that a large q parameter value can also trigger an overly long computation during some of these checks. A correct q value, if present, cannot be larger than the modulus p parameter, thus it is unnecessary to perform these checks if q is larger than p. An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack. The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check(). Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the "-check" option. The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.
Affected range | <1.1.1v-0~deb11u1 |
Fixed version | 1.1.1v-0~deb11u1 |
Description
Issue summary: Checking excessively long DH keys or parameters may be very slow. Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service. The function DH_check() performs various checks on DH parameters. One of those checks confirms that the modulus ('p' parameter) is not too large. Trying to use a very large modulus is slow and OpenSSL will not normally use a modulus which is over 10,000 bits in length. However the DH_check() function checks numerous aspects of the key or parameters that have been supplied. Some of those checks use the supplied modulus value even if it has already been found to be too large. An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulernable to a Denial of Service attack. The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check(). Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the '-check' option. The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.
Affected range | <1.1.1n-0+deb11u5 |
Fixed version | 1.1.1n-0+deb11u5 |
Description
The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification. As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function. Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument. Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.
Affected range | <1.1.1n-0+deb11u5 |
Fixed version | 1.1.1n-0+deb11u5 |
Description
Applications that use a non-default option when verifying certificates may be vulnerable to an attack from a malicious CA to circumvent certain checks. Invalid certificate policies in leaf certificates are silently ignored by OpenSSL and other certificate policy checks are skipped for that certificate. A malicious CA could use this to deliberately assert invalid certificate policies in order to circumvent policy checking on the certificate altogether. Policy processing is disabled by default but can be enabled by passing the
-policy' argument to the command line utilities or by calling the
X509_VERIFY_PARAM_set1_policies()' function.
Affected range | <1.1.1n-0+deb11u4 |
Fixed version | 1.1.1n-0+deb11u4 |
Description
AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was preexisting in the memory that wasn't written. In the special case of "in place" encryption, sixteen bytes of the plaintext would be revealed. Since OpenSSL does not support OCB based cipher suites for TLS and DTLS, they are both unaffected. Fixed in OpenSSL 3.0.5 (Affected 3.0.0-3.0.4). Fixed in OpenSSL 1.1.1q (Affected 1.1.1-1.1.1p).
Affected range | <1.1.1n-0+deb11u4 |
Fixed version | 1.1.1n-0+deb11u4 |
Description
The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications. The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash. This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7. Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream. The OpenSSL cms and smime command line applications are similarly affected.
Affected range | <1.1.1n-0+deb11u4 |
Fixed version | 1.1.1n-0+deb11u4 |
Description
The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue.
Affected range | <1.1.1n-0+deb11u4 |
Fixed version | 1.1.1n-0+deb11u4 |
Description
A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection.
ncurses 6.2+20201114-2
(deb)
pkg:deb/debian/ncurses@6.2+20201114-2?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | <6.2+20201114-2+deb11u2 |
Fixed version | 6.2+20201114-2+deb11u2 |
Description
ncurses before 6.4 20230408, when used by a setuid application, allows local users to trigger security-relevant memory corruption via malformed data in a terminfo database file that is found in $HOME/.terminfo or reached via the TERMINFO or TERM environment variable.
Affected range | <6.2+20201114-2+deb11u1 |
Fixed version | 6.2+20201114-2+deb11u1 |
Description
ncurses 6.3 before patch 20220416 has an out-of-bounds read and segmentation violation in convert_strings in tinfo/read_entry.c in the terminfo library.
libssh 0.9.5-1+deb11u1
(deb)
pkg:deb/debian/libssh@0.9.5-1+deb11u1?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | <0.9.7-0+deb11u1 |
Fixed version | 0.9.7-0+deb11u1 |
Description
A NULL pointer dereference was found In libssh during re-keying with algorithm guessing. This issue may allow an authenticated client to cause a denial of service.
Affected range | <0.9.8-0+deb11u1 |
Fixed version | 0.9.8-0+deb11u1 |
Description
A flaw was found in the libssh implements abstract layer for message digest (MD) operations implemented by different supported crypto backends. The return values from these were not properly checked, which could cause low-memory situations failures, NULL dereferences, crashes, or usage of the uninitialized memory as an input for the KDF. In this case, non-matching keys will result in decryption/integrity failures, terminating the connection.
Affected range | <0.9.8-0+deb11u1 |
Fixed version | 0.9.8-0+deb11u1 |
Description
A flaw was found in libssh. By utilizing the ProxyCommand or ProxyJump feature, users can exploit unchecked hostname syntax on the client. This issue may allow an attacker to inject malicious code into the command of the features mentioned through the hostname parameter.
Affected range | <0.9.8-0+deb11u1 |
Fixed version | 0.9.8-0+deb11u1 |
Description
The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3, Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust.
Affected range | <0.9.7-0+deb11u1 |
Fixed version | 0.9.7-0+deb11u1 |
Description
A vulnerability was found in libssh, where the authentication check of the connecting client can be bypassed in the
pki_verify_data_signature
function in memory allocation problems. This issue may happen if there is insufficient memory or the memory usage is limited. The problem is caused by the return valuerc,
which is initialized to SSH_ERROR and later rewritten to save the return value of the function callpki_key_check_hash_compatible.
The value of the variable is not changed between this point and the cryptographic verification. Therefore any error between them callsgoto error
returning SSH_OK.
systemd 247.3-7+deb11u1
(deb)
pkg:deb/debian/systemd@247.3-7+deb11u1?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | <247.3-7+deb11u2 |
Fixed version | 247.3-7+deb11u2 |
Description
A vulnerability was found in systemd. This security flaw can cause a local information leak due to systemd-coredump not respecting the fs.suid_dumpable kernel setting.
Affected range | <247.3-7+deb11u2 |
Fixed version | 247.3-7+deb11u2 |
Description
An off-by-one Error issue was discovered in Systemd in format_timespan() function of time-util.c. An attacker could supply specific values for time and accuracy that leads to buffer overrun in format_timespan(), leading to a Denial of Service.
libxml2 2.9.10+dfsg-6.7+deb11u3
(deb)
pkg:deb/debian/libxml2@2.9.10+dfsg-6.7+deb11u3?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | <2.9.10+dfsg-6.7+deb11u4 |
Fixed version | 2.9.10+dfsg-6.7+deb11u4 |
Description
An issue was discovered in libxml2 before 2.10.4. When hashing empty dict strings in a crafted XML document, xmlDictComputeFastKey in dict.c can produce non-deterministic values, leading to various logic and memory errors, such as a double free. This behavior occurs because there is an attempt to use the first byte of an empty string, and any value is possible (not solely the '\0' value).
Affected range | <2.9.10+dfsg-6.7+deb11u4 |
Fixed version | 2.9.10+dfsg-6.7+deb11u4 |
Description
In libxml2 before 2.10.4, parsing of certain invalid XSD schemas can lead to a NULL pointer dereference and subsequently a segfault. This occurs in xmlSchemaFixupComplexType in xmlschemas.c.
nghttp2 1.52.0-1+deb12u1
(deb)
pkg:deb/debian/nghttp2@1.52.0-1+deb12u1?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=1.43.0-1+deb11u1 |
Fixed version | Not Fixed |
Description
nghttp2 is an implementation of the Hypertext Transfer Protocol version 2 in C. The nghttp2 library prior to version 1.61.0 keeps reading the unbounded number of HTTP/2 CONTINUATION frames even after a stream is reset to keep HPACK context in sync. This causes excessive CPU usage to decode HPACK stream. nghttp2 v1.61.0 mitigates this vulnerability by limiting the number of CONTINUATION frames it accepts per stream. There is no workaround for this vulnerability.
dbus 1.12.24-0+deb11u1
(deb)
pkg:deb/debian/dbus@1.12.24-0+deb11u1?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | <1.12.28-0+deb11u1 |
Fixed version | 1.12.28-0+deb11u1 |
Description
D-Bus before 1.15.6 sometimes allows unprivileged users to crash dbus-daemon. If a privileged user with control over the dbus-daemon is using the org.freedesktop.DBus.Monitoring interface to monitor message bus traffic, then an unprivileged user with the ability to connect to the same dbus-daemon can cause a dbus-daemon crash under some circumstances via an unreplyable message. When done on the well-known system bus, this is a denial-of-service vulnerability. The fixed versions are 1.12.28, 1.14.8, and 1.15.6.
krb5 1.18.3-6+deb11u3
(deb)
pkg:deb/debian/krb5@1.18.3-6+deb11u3?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | <1.18.3-6+deb11u4 |
Fixed version | 1.18.3-6+deb11u4 |
Description
lib/kadm5/kadm_rpc_xdr.c in MIT Kerberos 5 (aka krb5) before 1.20.2 and 1.21.x before 1.21.1 frees an uninitialized pointer. A remote authenticated user can trigger a kadmind crash. This occurs because _xdr_kadm5_principal_ent_rec does not validate the relationship between n_key_data and the key_data array count.
glibc 2.36-9+deb12u7
(deb)
pkg:deb/debian/glibc@2.36-9+deb12u7?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | >=2.31-13+deb11u8 |
Fixed version | Not Fixed |
Description
In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(|)(\1\1)*' in grep, a different issue than CVE-2018-20796. NOTE: the software maintainer disputes that this is a vulnerability because the behavior occurs only with a crafted pattern
Affected range | >=2.31-13+deb11u8 |
Fixed version | Not Fixed |
Description
GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may guess the heap addresses of pthread_created thread. The component is: glibc. NOTE: the vendor's position is "ASLR bypass itself is not a vulnerability.
Affected range | >=2.31-13+deb11u8 |
Fixed version | Not Fixed |
Description
GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass ASLR using cache of thread stack and heap. The component is: glibc. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.
Affected range | >=2.31-13+deb11u8 |
Fixed version | Not Fixed |
Description
GNU Libc current is affected by: Re-mapping current loaded library with malicious ELF file. The impact is: In worst case attacker may evaluate privileges. The component is: libld. The attack vector is: Attacker sends 2 ELF files to victim and asks to run ldd on it. ldd execute code. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.
Affected range | >=2.31-13+deb11u8 |
Fixed version | Not Fixed |
Description
GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass stack guard protection. The component is: nptl. The attack vector is: Exploit stack buffer overflow vulnerability and use this bypass vulnerability to bypass stack guard. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.
Affected range | >=2.31-13+deb11u8 |
Fixed version | Not Fixed |
Description
In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(\227|)(\1\1|t1|\\2537)+' in grep.
Affected range | >=2.31-13+deb11u8 |
Fixed version | Not Fixed |
Description
The glob implementation in the GNU C Library (aka glibc or libc6) allows remote authenticated users to cause a denial of service (CPU and memory consumption) via crafted glob expressions that do not match any pathnames, as demonstrated by glob expressions in STAT commands to an FTP daemon, a different vulnerability than CVE-2010-2632.
pcre3 2:8.39-13
(deb)
pkg:deb/debian/pcre3@2:8.39-13?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | >=2:8.39-13 |
Fixed version | Not Fixed |
Description
libpcre in PCRE before 8.43 allows a subject buffer over-read in JIT when UTF is disabled, and \X or \R has more than one fixed quantifier, a related issue to CVE-2019-20454.
Affected range | >=2:8.39-13 |
Fixed version | Not Fixed |
Description
Stack-based buffer overflow in the pcre32_copy_substring function in pcre_get.c in libpcre1 in PCRE 8.40 allows remote attackers to cause a denial of service (WRITE of size 268) or possibly have unspecified other impact via a crafted file.
Affected range | >=2:8.39-13 |
Fixed version | Not Fixed |
Description
Stack-based buffer overflow in the pcre32_copy_substring function in pcre_get.c in libpcre1 in PCRE 8.40 allows remote attackers to cause a denial of service (WRITE of size 4) or possibly have unspecified other impact via a crafted file.
Affected range | >=2:8.39-13 |
Fixed version | Not Fixed |
Description
In PCRE 8.41, after compiling, a pcretest load test PoC produces a crash overflow in the function match() in pcre_exec.c because of a self-recursive call. NOTE: third parties dispute the relevance of this report, noting that there are options that can be used to limit the amount of stack that is used
Affected range | >=2:8.39-13 |
Fixed version | Not Fixed |
Description
In PCRE 8.41, the OP_KETRMAX feature in the match function in pcre_exec.c allows stack exhaustion (uncontrolled recursion) when processing a crafted regular expression.
openldap 2.4.57+dfsg-3+deb11u1
(deb)
pkg:deb/debian/openldap@2.4.57+dfsg-3+deb11u1?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | >=2.4.57+dfsg-3+deb11u1 |
Fixed version | Not Fixed |
Description
libldap in certain third-party OpenLDAP packages has a certificate-validation flaw when the third-party package is asserting RFC6125 support. It considers CN even when there is a non-matching subjectAltName (SAN). This is fixed in, for example, openldap-2.4.46-10.el8 in Red Hat Enterprise Linux.
Affected range | >=2.4.57+dfsg-3+deb11u1 |
Fixed version | Not Fixed |
Description
contrib/slapd-modules/nops/nops.c in OpenLDAP through 2.4.45, when both the nops module and the memberof overlay are enabled, attempts to free a buffer that was allocated on the stack, which allows remote attackers to cause a denial of service (slapd crash) via a member MODDN operation.
Affected range | >=2.4.57+dfsg-3+deb11u1 |
Fixed version | Not Fixed |
Description
slapd in OpenLDAP 2.4.45 and earlier creates a PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for PID file modification before a root script executes a "kill
cat /pathname
" command, as demonstrated by openldap-initscript.
Affected range | >=2.4.57+dfsg-3+deb11u1 |
Fixed version | Not Fixed |
Description
The nss_parse_ciphers function in libraries/libldap/tls_m.c in OpenLDAP does not properly parse OpenSSL-style multi-keyword mode cipher strings, which might cause a weaker than intended cipher to be used and allow remote attackers to have unspecified impact via unknown vectors.
openldap 2.5.13+dfsg-5
(deb)
pkg:deb/debian/openldap@2.5.13+dfsg-5?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=2.4.57+dfsg-3+deb11u1 |
Fixed version | Not Fixed |
Description
libldap in certain third-party OpenLDAP packages has a certificate-validation flaw when the third-party package is asserting RFC6125 support. It considers CN even when there is a non-matching subjectAltName (SAN). This is fixed in, for example, openldap-2.4.46-10.el8 in Red Hat Enterprise Linux.
Affected range | >=2.4.57+dfsg-3+deb11u1 |
Fixed version | Not Fixed |
Description
contrib/slapd-modules/nops/nops.c in OpenLDAP through 2.4.45, when both the nops module and the memberof overlay are enabled, attempts to free a buffer that was allocated on the stack, which allows remote attackers to cause a denial of service (slapd crash) via a member MODDN operation.
Affected range | >=2.4.57+dfsg-3+deb11u1 |
Fixed version | Not Fixed |
Description
slapd in OpenLDAP 2.4.45 and earlier creates a PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for PID file modification before a root script executes a "kill
cat /pathname
" command, as demonstrated by openldap-initscript.
Affected range | >=2.4.57+dfsg-3+deb11u1 |
Fixed version | Not Fixed |
Description
The nss_parse_ciphers function in libraries/libldap/tls_m.c in OpenLDAP does not properly parse OpenSSL-style multi-keyword mode cipher strings, which might cause a weaker than intended cipher to be used and allow remote attackers to have unspecified impact via unknown vectors.
curl 7.88.1-10+deb12u5
(deb)
pkg:deb/debian/curl@7.88.1-10+deb12u5?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=7.74.0-1.3+deb11u11 |
Fixed version | Not Fixed |
Description
libcurl skips the certificate verification for a QUIC connection under certain conditions, when built to use wolfSSL. If told to use an unknown/bad cipher or curve, the error path accidentally skips the verification and returns OK, thus ignoring any certificate problems.
Affected range | >=7.74.0-1.3+deb11u11 |
Fixed version | Not Fixed |
Description
A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different backends for resolving host names, selected at build time. If it is built to use the synchronous resolver, it allows name resolves to time-out slow operations using
alarm()
andsiglongjmp()
. When doing this, libcurl used a global buffer that was not mutex protected and a multi-threaded application might therefore crash or otherwise misbehave.
Affected range | >=7.74.0-1.3+deb11u11 |
Fixed version | Not Fixed |
Description
When curl is instructed to get content using the metalink feature, and a user name and password are used to download the metalink XML file, those same credentials are then subsequently passed on to each of the servers from which curl will download or try to download the contents from. Often contrary to the user's expectations and intentions and without telling the user it happened.
Affected range | >=7.74.0-1.3+deb11u11 |
Fixed version | Not Fixed |
Description
When curl is instructed to download content using the metalink feature, thecontents is verified against a hash provided in the metalink XML file.The metalink XML file points out to the client how to get the same contentfrom a set of different URLs, potentially hosted by different servers and theclient can then download the file from one or several of them. In a serial orparallel manner.If one of the servers hosting the contents has been breached and the contentsof the specific file on that server is replaced with a modified payload, curlshould detect this when the hash of the file mismatches after a completeddownload. It should remove the contents and instead try getting the contentsfrom another URL. This is not done, and instead such a hash mismatch is onlymentioned in text and the potentially malicious content is kept in the file ondisk.
sqlite3 3.34.1-3
(deb)
pkg:deb/debian/sqlite3@3.34.1-3?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | >=3.34.1-3 |
Fixed version | Not Fixed |
Description
SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a string argument to a C API.
Affected range | >=3.34.1-3 |
Fixed version | Not Fixed |
Description
A Memory Leak vulnerability exists in SQLite Project SQLite3 3.35.1 and 3.37.0 via maliciously crafted SQL Queries (made via editing the Database File), it is possible to query a record, and leak subsequent bytes of memory that extend beyond the record, which could let a malicious user obtain sensitive information. NOTE: The developer disputes this as a vulnerability stating that If you give SQLite a corrupted database file and submit a query against the database, it might read parts of the database that you did not intend or expect.
Affected range | >=3.34.1-3 |
Fixed version | Not Fixed |
Description
A segmentation fault can occur in the sqlite3.exe command-line component of SQLite 3.36.0 via the idxGetTableInfo function when there is a crafted SQL query. NOTE: the vendor disputes the relevance of this report because a sqlite3.exe user already has full privileges (e.g., is intentionally allowed to execute commands). This report does NOT imply any problem in the SQLite library.
shadow 1:4.8.1-1
(deb)
pkg:deb/debian/shadow@1:4.8.1-1?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | >=1:4.8.1-1 |
Fixed version | Not Fixed |
Description
shadow 4.8, in certain circumstances affecting at least Gentoo, Arch Linux, and Void Linux, allows local users to obtain root access because setuid programs are misconfigured. Specifically, this affects shadow 4.8 when compiled using --with-libpam but without explicitly passing --disable-account-tools-setuid, and without a PAM configuration suitable for use with setuid account management tools. This combination leads to account management tools (groupadd, groupdel, groupmod, useradd, userdel, usermod) that can easily be used by unprivileged local users to escalate privileges to root in multiple ways. This issue became much more relevant in approximately December 2019 when an unrelated bug was fixed (i.e., the chmod calls to suidusbins were fixed in the upstream Makefile which is now included in the release version 4.8).
Affected range | >=1:4.8.1-1 |
Fixed version | Not Fixed |
Description
shadow: TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees
Affected range | >=1:4.8.1-1 |
Fixed version | Not Fixed |
Description
initscripts in rPath Linux 1 sets insecure permissions for the /var/log/btmp file, which allows local users to obtain sensitive information regarding authentication attempts. NOTE: because sshd detects the insecure permissions and does not log certain events, this also prevents sshd from logging failed authentication attempts by remote attackers.
openssl 3.0.11-1~deb12u2
(deb)
pkg:deb/debian/openssl@3.0.11-1~deb12u2?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=1.1.1w-0+deb11u1 |
Fixed version | Not Fixed |
Description
OpenSSL 0.9.8i on the Gaisler Research LEON3 SoC on the Xilinx Virtex-II Pro FPGA uses a Fixed Width Exponentiation (FWE) algorithm for certain signature calculations, and does not verify the signature before providing it to a caller, which makes it easier for physically proximate attackers to determine the private key via a modified supply voltage for the microprocessor, related to a "fault-based attack."
Affected range | >=1.1.1w-0+deb11u1 |
Fixed version | Not Fixed |
Description
The NIST SP 800-90A default statement of the Dual Elliptic Curve Deterministic Random Bit Generation (Dual_EC_DRBG) algorithm contains point Q constants with a possible relationship to certain "skeleton key" values, which might allow context-dependent attackers to defeat cryptographic protection mechanisms by leveraging knowledge of those values. NOTE: this is a preliminary CVE for Dual_EC_DRBG; future research may provide additional details about point Q and associated attacks, and could potentially lead to a RECAST or REJECT of this CVE.
perl 5.36.0-7+deb12u1
(deb)
pkg:deb/debian/perl@5.36.0-7+deb12u1?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=5.32.1-4+deb11u3 |
Fixed version | Not Fixed |
Description
HTTP::Tiny before 0.083, a Perl core module since 5.13.9 and available standalone on CPAN, has an insecure default TLS configuration where users must opt in to verify certificates.
Affected range | >=5.32.1-4+deb11u3 |
Fixed version | Not Fixed |
Description
_is_safe in the File::Temp module for Perl does not properly handle symlinks.
m4 1.4.19-3
(deb)
pkg:deb/debian/m4@1.4.19-3?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=1.4.18-5 |
Fixed version | Not Fixed |
Description
Unspecified vulnerability in GNU m4 before 1.4.11 might allow context-dependent attackers to execute arbitrary code, related to improper handling of filenames specified with the -F option. NOTE: it is not clear when this issue crosses privilege boundaries.
Affected range | >=1.4.18-5 |
Fixed version | Not Fixed |
Description
The (1) maketemp and (2) mkstemp builtin functions in GNU m4 before 1.4.11 do not quote their output when a file is created, which might allow context-dependent attackers to trigger a macro expansion, leading to unspecified use of an incorrect filename.
util-linux 2.36.1-8+deb11u1
(deb)
pkg:deb/debian/util-linux@2.36.1-8+deb11u1?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | >=2.36.1-8+deb11u1 |
Fixed version | Not Fixed |
Description
A flaw was found in the util-linux chfn and chsh utilities when compiled with Readline support. The Readline library uses an "INPUTRC" environment variable to get a path to the library config file. When the library cannot parse the specified file, it prints an error message containing data from the file. This flaw allows an unprivileged user to read root-owned files, potentially leading to privilege escalation. This flaw affects util-linux versions prior to 2.37.4.
Affected range | <2.36.1-8+deb11u2 |
Fixed version | 2.36.1-8+deb11u2 |
Description
wall in util-linux through 2.40, often installed with setgid tty permissions, allows escape sequences to be sent to other users' terminals through argv. (Specifically, escape sequences received from stdin are blocked, but escape sequences received from argv are not blocked.) There may be plausible scenarios where this leads to account takeover.
tar 1.34+dfsg-1
(deb)
pkg:deb/debian/tar@1.34+dfsg-1?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | <1.34+dfsg-1+deb11u1 |
Fixed version | 1.34+dfsg-1+deb11u1 |
Description
GNU Tar through 1.34 has a one-byte out-of-bounds read that results in use of uninitialized memory for a conditional jump. Exploitation to change the flow of control has not been demonstrated. The issue occurs in from_header in list.c via a V7 archive in which mtime has approximately 11 whitespace characters.
Affected range | <1.34+dfsg-1+deb11u1 |
Fixed version | 1.34+dfsg-1+deb11u1 |
Description
In GNU tar before 1.35, mishandled extension attributes in a PAX archive can lead to an application crash in xheader.c.
glib2.0 2.74.6-2+deb12u2
(deb)
pkg:deb/debian/glib2.0@2.74.6-2+deb12u2?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=2.66.8-1+deb11u1 |
Fixed version | Not Fixed |
Description
GLib 2.31.8 and earlier, when the g_str_hash function is used, computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table. NOTE: this issue may be disputed by the vendor; the existence of the g_str_hash function is not a vulnerability in the library, because callers of g_hash_table_new and g_hash_table_new_full can specify an arbitrary hash function that is appropriate for the application.
gnupg2 2.2.27-2+deb11u2
(deb)
pkg:deb/debian/gnupg2@2.2.27-2+deb11u2?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | >=2.2.27-2+deb11u2 |
Fixed version | Not Fixed |
Description
GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.
pcre2 10.36-2+deb11u1
(deb)
pkg:deb/debian/pcre2@10.36-2+deb11u1?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | >=10.36-2+deb11u1 |
Fixed version | Not Fixed |
Description
Integer overflow vulnerability in pcre2test before 10.41 allows attackers to cause a denial of service or other unspecified impacts via negative input.
libgcrypt20 1.8.7-6
(deb)
pkg:deb/debian/libgcrypt20@1.8.7-6?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | >=1.8.7-6 |
Fixed version | Not Fixed |
Description
cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for Libgcrypt's ElGamal implementation.
gnutls28 3.7.9-2+deb12u2
(deb)
pkg:deb/debian/gnutls28@3.7.9-2+deb12u2?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=3.7.1-5+deb11u4 |
Fixed version | Not Fixed |
Description
The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS session, in conjunction with JavaScript code that uses (1) the HTML5 WebSocket API, (2) the Java URLConnection API, or (3) the Silverlight WebClient API, aka a "BEAST" attack.
net-tools 2.10-0.1
(deb)
pkg:deb/debian/net-tools@2.10-0.1?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=1.60+git20181103.0eebece-1 |
Fixed version | Not Fixed |
Description
ifconfig, when used on the Linux kernel 2.2 and later, does not report when the network interface is in promiscuous mode if it was put in promiscuous mode using PACKET_MR_PROMISC, which could allow attackers to sniff the network without detection, as demonstrated using libpcap.
coreutils 8.32-4+b1
(deb)
pkg:deb/debian/coreutils@8.32-4+b1?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | >=8.32-4 |
Fixed version | Not Fixed |
Description
In GNU Coreutils through 8.29, chown-core.c in chown and chgrp does not prevent replacement of a plain file with a symlink during use of the POSIX "-R -L" options, which allows local users to modify the ownership of arbitrary files by leveraging a race condition.
apt 2.2.4
(deb)
pkg:deb/debian/apt@2.2.4?os_distro=bullseye&os_name=debian&os_version=11
# prod.Dockerfile (7:14)
FROM greenbone/gvm-libs:$VERSION AS build
COPY . /source
RUN sh /source/.github/install-openvas-dependencies.sh
COPY --from=openvas-smb /usr/local/lib/ /usr/local/lib/
RUN cmake -DCMAKE_BUILD_TYPE=Release -DINSTALL_OLD_SYNC_SCRIPT=OFF -B/build /source
RUN DESTDIR=/install cmake --build /build -- install
FROM greenbone/gvm-libs:$VERSION
Affected range | >=2.2.4 |
Fixed version | Not Fixed |
Description
It was found that apt-key in apt, all versions, do not correctly validate gpg keys with the master keyring, leading to a potential man-in-the-middle attack.
hiredis 0.14.1-3
(deb)
pkg:deb/debian/hiredis@0.14.1-3?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=0.14.1-1 |
Fixed version | Not Fixed |
Description
Hiredis is a minimalistic C client library for the Redis database. In affected versions Hiredis is vulnurable to integer overflow if provided maliciously crafted or corrupted
RESP
mult-bulk
protocol data. When parsingmulti-bulk
(array-like) replies, hiredis fails to check ifcount * sizeof(redisReply*)
can be represented inSIZE_MAX
. If it can not, and thecalloc()
call doesn't itself make this check, it would result in a short allocation and subsequent buffer overflow. Users of hiredis who are unable to update may set the maxelements context option to a value small enough that no overflow is possible.
nmap 7.93+dfsg1-1
(deb)
pkg:deb/debian/nmap@7.93+dfsg1-1?os_distro=bullseye&os_name=debian&os_version=11
Affected range | >=7.91+dfsg1+really7.80+dfsg1-2 |
Fixed version | Not Fixed |
Description
Nmap through 7.70, when the -sV option is used, allows remote attackers to cause a denial of service (stack consumption and application crash) via a crafted TCP-based service.
7ca2d44
to
908afab
Compare
908afab
to
c102446
Compare
c102446
to
6f9340b
Compare
8f7db5f
to
0e2468e
Compare
0e2468e
to
94045cf
Compare
874c51d
to
7b7f406
Compare
5ca2d1c
to
c6ddab5
Compare
To simulate forking behaviour for sripts that rely on it e.g.: ``` set_kb_item(name: "test", value: 1); set_kb_item(name: "test", value: 2); set_kb_item(name: "test", value: 3); set_kb_item(name: "test", value: 4); set_kb_item(name: "test", value: 5); display(get_kb_item("test")); ``` a new NaslValue `Fork` is introduced. When a method returns `Fork` then the interpreter is cloning the register and creates as many interpreter instances as elements within `Fork` so that a caller can then call those interpreter after each statement.
Adds possibility to simplify StatementIteration through all interpreter forks. Usage: ``` use nasl_syntax::NaslValue; use nasl_interpreter::{Interpreter, Register, ContextBuilder, StatementIterator}; let register = Register::default(); let context_builder = ContextBuilder::default(); let context = context_builder.build(); let code = r#" set_kb_item(name: "test", value: 1); set_kb_item(name: "test", value: 2); display(get_kb_item("test")); "#; let mut interpreter = Interpreter::new(register, &context); let mut results = vec![]; for r in nasl_syntax::parse(code){ for r in StatementIterator::new(&mut interpreter, r.expect("parseable")) { results.push(r.expect("executable")); } } assert_eq!(results, vec![NaslValue::Null; 4]); ```
Adds interpreter that should be used when a code str is available. It simplifies the usage so that a user doesn't need to call parse and creaet an interpreter instance manually. ``` use nasl_syntax::NaslValue; use nasl_interpreter::{Register, ContextBuilder, CodeInterpreter}; let register = Register::default(); let context_builder = ContextBuilder::default(); let context = context_builder.build(); let code = r#" set_kb_item(name: "test", value: 1); set_kb_item(name: "test", value: 2); display(get_kb_item("test")); "#; let interpreter = CodeInterpreter::new(code, register, &context); let results = interpreter.filter_map(|x|x.ok()).collect::<Vec<_>>(); assert_eq!(results, vec![NaslValue::Null; 5]); ```
On fork instead of storing complete interpreter we just store a list of register, position and return values. That way the interpreter handling can be streamlined.
As the Interpreter can already iterate through Statements the StatementIterator as a struct is not required anymore.
c6ddab5
to
afbf181
Compare
To simulate forking behaviour for sripts that rely on it e.g.:
a new NaslValue
Fork
is introduced. When a method returnsFork
thenthe interpreter is cloning the register and creates as many interpreter
instances as elements within
Fork
so that a caller can then call thoseinterpreter after each statement.
SC-1069